Custom partitioning of a data stream

ABSTRACT

Techniques for partitioning data streams are provided. In some examples, a query for processing at least a portion of a data stream may be identified. The data stream may be associated with a user. Additionally, in some examples, code identifying an attribute of the identified stream may be received. The code may be capable of configuring the query based at least in part on the attribute. Further, in some aspects, the code may be configured to partition the data stream into at least a sub-stream based at least in part on the attribute.

BACKGROUND

Event processing applications can be configured to process very large amounts of streaming data from many disparate sources. In some cases, the streaming data may be associated with multiple different attributes. For example, a stream of customer data associated with accessing network content of a company may include Internet Protocol (IP) addresses and/or geographic location information associated with the customers. Often, the data streams are received at very high rates and include nearly unmanageable amounts of information. With a wide variety of input streams and data parameters, and the ever increasing speed of and volume of information received, it can become burdensome to manage such data streams.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the FIG. 1 in which the reference number first appears. The use of the same reference numbers in different FIGS. indicates similar or identical items.

FIG. 1 is a simplified block diagram illustrating an example architecture for managing custom partitioning of data streams as described herein, according to at least one example.

FIG. 2 is a simplified block diagram illustrating at least some features of an event processing engine capable of handling continuous streams of data as described herein, according to at least one example.

FIG. 3 is a simplified block diagram illustrating at least some features of a custom configuration service configured to implement the custom partitioning of data streams described herein, according to at least one example.

FIG. 4 is a simplified flow diagram illustrating at least some techniques for the custom partitioning of data streams described herein, according to at least one example.

FIG. 5 is a simplified flow diagram illustrating at least one process for implementing the custom partitioning of data streams described herein, according to at least one example.

FIG. 6 is a simplified flow diagram illustrating at least one process for implementing the custom partitioning of data streams described herein, according to at least one example.

FIG. 7 depicts a simplified diagram of a distributed system for implementing some of the examples described herein, according to at least one example.

FIG. 8 is a simplified block diagram of components of a system environment by which services provided by the components of an embodiment system may be offered as cloud services, in accordance with some of the examples described herein, according to at least one example.

FIG. 9 illustrates an exemplary computer system, in which various embodiments of the present disclosure may be implemented in according with some of the examples described herein, according to at least one example.

BRIEF SUMMARY

In the following description, various embodiments will be described. For purposes of explanation, specific configurations and details are set forth in order to provide a thorough understanding of the embodiments. However, it will also be apparent to one skilled in the art that the embodiments may be practiced without the specific details. Furthermore, well-known features may be omitted or simplified in order not to obscure the embodiment being described.

According to one embodiment, a system may be configured with a memory and a processor. The processor may be configured to execute instructions stored on the memory to identify a data stream associated with the user. The processor may also be configured to execute the instructions to receive a query for processing at least a portion of the identified data stream and receive, from the user, code identifying an attribute of the identified data stream, the code capable of configuring the query based at least in part on the attribute. In some aspects, the process may be configured to execute the instructions to associate, by the computer system, the code with the query and configure the query to partition the data stream based at least in part on the attribute after the code is associated with the query. The instructions may also be executed to partition the data stream into a plurality of portions based at least in part on the attribute, provide a sub-stream for at least one of the plurality of portions to the query, and provide results of the query based at least in part on the provided sub-stream.

In some examples, the code comprises an object-oriented class based at least in part on a contract provided to the user, and configuring the query comprises tying the query to the object-oriented class. The instructions may also be executed to receive an event of the data stream based at least in part on the query, provide the event to the object-oriented class, and receive an output from the object-oriented class. The data stream may be partitioned based at least in part on the output from the object-oriented class. The attribute may comprise at least one of a first identifier of a computing device of a customer of the user, a second identifier of an item associated with the user, or a third identifier of an item attribute associated with the item. The identifier of the computing device of the customer may indicate an Internet Protocol address of the computing device of the customer or a geographic region in which the computing device of the customer is located.

According to another embodiment, a computer-readable medium may include instructions that, when executed, configure a computer processor to identify a query for processing at least a portion of a data stream associated with a user. The instructions may further configure the processor to receive, from the user, code identifying an attribute of the identified data stream, the code capable of configuring the query based at least in part on the attribute. The instructions may also configure the processor to configure the query to process one or more sub-streams of the data stream based at least in part on the attribute.

In some examples, the plurality of instructions may further comprise instructions that cause the one or more processors to process a plurality of the one or more sub-streams in parallel. The code may comprise a java class based at least in part on a java contract provided to the user. The plurality of instructions may further comprise instructions that cause the one or more processors to receive an event of the data stream based at least in part on the query and provide the event to the java class. The plurality of instructions may further comprise instructions that cause the one or more processors to implement the java class to process the event based at least in part on the attribute and receive an output from the java class. In some examples, the output from the java class may be at least one of the one or more sub-streams. The attribute may be specified by the user prior to receipt of the code. In some examples, at least one sub-stream of the one or more sub-streams may be generated based at least in part on a hashing function performed on the at least a portion of the data stream.

According to another embodiment, a method may be executed by a computer system to at least identify, by a computing system, a data stream associated with a user. The method may also receive a query for processing at least a portion of the identified data stream. The method may also receive, from the user, code identifying an attribute of the identified data stream, the code capable of configuring the query based at least in part on the attribute. The method may also configure the code to partition the data stream into at least one sub-stream based at least in part on the attribute and process the at least one sub-stream using the received query.

In some cases, the method may also associate the code with the query. The at least one sub-stream may be processed, using the received query, in parallel with at least a second sub-stream received as an output from the code. The method may also receive an event of the data stream based at least in part on the query and provide the event to a java class that corresponds to the received code. In some instances, the method may implement the java class to process the event based at least in part on the attribute and receive an output from the java class that identifies the at least one sub-stream. The data stream may be partitioned based at least in part on the java class. The sub-stream may be generated based at least in part on a hashing function performed on at least one of the plurality of portions. Additionally, the attribute may comprise at least one of an Internet Protocol address associated with a customer of the user or a geographic region associated with the customer of the user.

The foregoing, together with other features and embodiments will become more apparent upon referring to the following specification, claims, and accompanying drawings.

DETAILED DESCRIPTION

In the following description, various embodiments will be described. For purposes of explanation, specific configurations and details are set forth in order to provide a thorough understanding of the embodiments. However, it will also be apparent to one skilled in the art that the embodiments may be practiced without the specific details. Furthermore, well-known features may be omitted or simplified in order not to obscure the embodiment being described.

Embodiments of the present disclosure are directed to, among other things, providing a custom (e.g., customizable) mechanism for partitioning streaming data. In some examples, this custom mechanism may be provided within an event processing and/or business intelligence framework. For example, an event processing framework may be configured to process streaming data from one or more sources (e.g., third-party streaming sources or the like) and manage, store, and/or output the data in one or more formats (e.g., as a stream and/or one or more sub-streams). As noted, a customizable mechanism may be provided that enables one or more users, customers, etc., to configure the event processing framework (e.g., utilizing an event processing engine) to partition one or more incoming streams based at least in part on custom parameters.

In one non-limiting example, a customer may develop and/or provide a query (e.g., a continuous query) for querying data from an incoming data stream. The stream may be received by a service provider that processes the stream using the query for the customer; however, in other examples, the customer may have the data processed using the query without the use of a service provider. In either event, the customer may also provide some configuration information that identifies one or more attributes of the data stream for partitioning. For example, the data of the data stream may include any number and/or type of attributes (e.g., an IP address associated with the data, a geographic location (or region) associated with the data, a user identifier (ID) associated the data, etc.). Based on the configuration information, the service provider may be configured to identify the attribute listed in the configuration information, extract or otherwise collect events associated with the identified attribute, and provide (e.g., as an output data stream such as, but not limited to, a sub-stream) the extracted and/or collected events associated with that attribute. The output sub-streams may be processed using one or more queries including post-processing such as, but not limited to, filtering, aggregating, etc. Thus, after the code partitions the event stream into sub-streams, downstream query processing may occur. In this way, a customer (also referred to herein as a user) may configure the service provider to partition the incoming data streams based at least in part on selected event attributes. Additionally, the user may fully customize the partitioning and/or provide code to fully customize the partitioning of the incoming data streams.

In some examples, the service provider may be configured to support continuous query language (CQL) queries (also referred to as “query statements”) on one or more data streams. Additionally, in some examples, mechanisms for supporting the CQL queries may also enable configuration of scripting code executed by the service providers (e.g., JavaScript or the like). This code may be configured, generated, managed, updated, and/or otherwise manipulated by a user, administrator, or other entity associated with the event data (e.g., business event data).

In general, a continuous data stream (also referred to as an event stream) may include a stream of data or events that may be continuous or unbounded in nature with no explicit end. Logically, an event or data stream may be a sequence of data elements (also referred to as events), each data element having an associated timestamp. A continuous event stream may be logically represented as a bag or set of elements (s, T), where “s” represents the data portion, and “T” is in the time domain. The “s” portion is generally referred to as a tuple or event. An event stream may thus be a sequence of time-stamped tuples or events.

In some aspects, the timestamps associated with events in a stream may equate to a clock time. In other examples, however, the time associated with events in an event stream may be defined by the application domain and may not correspond to clock time but may, for example, be represented by sequence numbers instead. Accordingly, the time information associated with an event in an event stream may be represented by a number, a timestamp, or any other information that represents a notion of time. For a system receiving an input event stream, the events arrive at the system in the order of increasing timestamps. There could be more than one event with the same timestamp.

In some examples, an event in an event stream may represent an occurrence of some worldly event (e.g., when a temperature sensor changed value to a new value, when the price of a stock symbol changed) and the time information associated with the event may indicate when the worldly event represented by the data stream event occurred. Additionally, attributes associated with each event may indicate particular (e.g., relevant) information (e.g., stored as metadata) about the worldly event such as, but not limited to, a user and/or item associated with the worldly event (e.g., a purchaser ID, a seller ID, a product ID, a price of the item, a location of the user, etc.), weather at a location during the worldly event, or the like.

For events received via an event stream, the time information associated with an event may be used to ensure that the events in the event stream arrive in the order of increasing timestamp values. This may enable events received in the event stream to be ordered based upon their associated time information. In order to enable this ordering, timestamps may be associated with events in an event stream in a non-decreasing manner such that a later-generated event has a later timestamp than an earlier-generated event. As another example, if sequence numbers are being used as time information, then the sequence number associated with a later-generated event may be greater than the sequence number associated with an earlier-generated event. In some examples, multiple events may be associated with the same timestamp or sequence number, for example, when the worldly events represented by the data stream events occur at the same time. Events belonging to the same event stream may generally be processed in the order imposed on the events by the associated time information, with earlier events being processed prior to later events.

The time information (e.g., timestamps) associated with an event in an event stream may be set by the source of the stream or alternatively may be set by the system receiving the stream. For example, in certain embodiments, a heartbeat may be maintained on a system receiving an event stream, and the time associated with an event may be based upon a time of arrival of the event at the system as measured by the heartbeat. It is possible for two events in an event stream to have the same time information. It is to be noted that while timestamp ordering requirement is specific to one event stream, events of different streams could be arbitrarily interleaved.

An event stream may have an associated schema “S,” the schema comprising time information and a set of one or more named attributes. All events that belong to a particular event stream conform to the schema associated with that particular event stream. Accordingly, for an event stream (s, T), the event stream may have a schema ‘S’ as (<time_stamp>, <attribute(s)>), where <attributes> represents the data portion of the schema and can comprise one or more attributes. For example, the schema for a stock ticker event stream may comprise attributes <stock symbol>, and <stock price>. Each event received via such a stream will have a time stamp and one or more attributes. For example, the stock ticker event stream may receive the following events and associated timestamps:

-   -   . . .     -   (<timestamp_N>, <NVDA,4>)     -   (<timestamp_N+1>, <ORCL,62>)     -   (<timestamp_N+2>, <PCAR,38>)     -   (<timestamp_N+3>, <SPOT,53>)     -   (<timestamp_N+4>, <PDCO,44>)     -   (<timestamp_N+5>, <PTEN,50>)     -   . . .         In the above stream, for stream element (<timestamp_N+1>,         <ORCL,62>), the event is <ORCL,62> with attributes         “stock_symbol” and “stock_value.” The timestamp associated with         the stream element is “timestamp_N+1.” A continuous event stream         is thus a flow of events, each event having a series (in some         examples, the same series) of attributes.

As noted, a stream may be the principle source of data that CQL queries may act on. A stream S may be a bag (also referred to as a “multi-set”) of elements (s, T), where “s” is in the schema of S and “T” is in the time domain. Additionally, stream elements may be tuple-timestamp pairs, which can be represented as a sequence of timestamped tuple insertions. In other words, a stream may be a sequence of timestamped tuples. In some cases, there may be more than one tuple with the same timestamp. And, the tuples of an input stream may be requested to arrive at the system in order of increasing timestamps. Further, as used herein, a continuous query may generally be capable of processing data of (i.e., queried against) a stream.

In the following description, for the purposes of explanation, specific details are set forth in order to provide a thorough understanding of embodiments of the disclosure. However, it will be apparent that various embodiments may be practiced without these specific details. The figures and description are not intended to be restrictive.

Systems depicted in some of the figures may be provided in various configurations. In some embodiments, the systems may be configured as a distributed system where one or more components of the system are distributed across one or more networks in a cloud computing system.

FIG. 1 depicts a simplified example system or architecture 100 in which techniques for managing configurable/custom partitions of a data stream may be implemented. In architecture 100, one or more users 102 (e.g., account holders) may utilize user computing devices 104(1)-(N) (collectively, “user devices 104”) to access one or more service provider computers 106 via one or more networks 108. In some aspects, the service provider computers 106 may also be in communication with one or more streaming data source computers 110 and/or one or more databases 112 via the networks 108. For example, the users 102 may utilize the service provider computers 106 to access or otherwise manage data of the streaming data source computers 110 and/or the databases 112 (e.g., queries may be used to process data of either or both of the streaming data source computers 110 or the databases 112). The databases 112 may be relational databases, SQL servers, or the like and may, in some examples, manage historical data, event data, relations, archived relations, or the like on behalf of the users 102. Additionally, the databases 112 may receive or otherwise store data provided by the streaming data source computers 110. In some examples, the users 102 may utilize the user devices 104 to interact with the service provider computers 106 by providing queries (also referred to as “query statements”) or other requests for data (e.g., historical event data, streaming event data, etc.). Such queries or requests may then be executed by the service provider computers 106 to process data of the databases 112 and/or incoming data from the streaming data source computers 110 (e.g., continuously querying incoming data as the incoming data is pushed to the query). Further, in some examples, the streaming data source computers 110 and/or the databases 112 may be part of an integrated, distributed environment associated with the service provider computers 106.

In some examples, the networks 108 may include any one or a combination of multiple different types of networks, such as cable networks, the Internet, wireless networks, cellular networks, intranet systems, and/or other private and/or public networks. While the illustrated example represents the users 102 accessing the service provider computers 106 over the networks 108, the described techniques may equally apply in instances where the users 102 interact with one or more service provider computers 106 via the one or more user devices 104 over a landline phone, via a kiosk, or in any other manner. It is also noted that the described techniques may apply in other client/server arrangements (e.g., set-top boxes, etc.), as well as in non-client/server arrangements (e.g., locally stored applications, etc.).

The user devices 104 may be any type of computing device such as, but not limited to, a mobile phone, a smart phone, a personal digital assistant (PDA), a laptop computer, a desktop computer, a thin-client device, a tablet PC, etc. In some examples, the user devices 104 may be in communication with the service provider computers 106 via the networks 108, or via other network connections. The user devices 104 may also be configured to provide one or more queries or query statements for requesting data of the databases 112 (or other data stores) to be processed. The user devices 104 may also be configured to provide code for configuring the service provider computers 106 to partition incoming event data based at least in part on the code. For example, the user computers 104 may provide an extensible hypertext markup language (XML), a user-configured java class, or the like that the service provider computers 106 can execute in order to implement a JavaScript for partitioning the incoming streams as appropriate.

In some aspects, the service provider computers 106 may also be any type of computing devices such as, but not limited to, mobile, desktop, thin-client, and/or cloud computing devices, such as servers. In some examples, the service provider computers 106 may be in communication with the user devices 104 via the networks 108, or via other network connections. The service provider computers 106 may include one or more servers, perhaps arranged in a cluster, as a server farm, or as individual servers not associated with one another. These servers may be configured to perform or otherwise host features described herein including, but not limited to, the management custom partitions for event streams described herein. Additionally, in some aspects, the service provider computers 106 may be configured as part of an integrated, distributed computing environment that includes the streaming data source computers 110 and/or the databases 112.

In one illustrative configuration, the service provider computers 106 may include at least one memory 136 and one or more processing units (or processor(s)) 138. The processor(s) 138 may be implemented as appropriate in hardware, computer-executable instructions, firmware, or combinations thereof. Computer-executable instruction or firmware implementations of the processor(s) 138 may include computer-executable or machine-executable instructions written in any suitable programming language to perform the various functions described.

The memory 136 may store program instructions that are loadable and executable on the processor(s) 138, as well as data generated during the execution of these programs. Depending on the configuration and type of service provider computers 106, the memory 136 may be volatile (such as random access memory (RAM)) and/or non-volatile (such as read-only memory (ROM), flash memory, etc.). The service provider computers 106 or servers may also include additional storage 140, which may include removable storage and/or non-removable storage. The additional storage 140 may include, but is not limited to, magnetic storage, optical disks, and/or tape storage. The disk drives and their associated computer-readable media may provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for the computing devices. In some implementations, the memory 136 may include multiple different types of memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), or ROM.

The memory 136, the additional storage 140, both removable and non-removable, are all examples of computer-readable storage media (and may be non-transitory). For example, computer-readable storage media may include volatile or non-volatile, removable or non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. The memory 136 and the additional storage 140 are all examples of computer storage media.

Alternatively, computer-readable communication media may include computer-readable instructions, program modules, or other data transmitted within a data signal, such as a carrier wave, or other transmission. However, as used herein, computer-readable storage media does not include computer-readable communication media.

The service provider computers 106 may also contain communications connection(s) 142 that allow the service provider computers 106 to communicate with a stored database, another computing device or server, user terminals, and/or other devices on the networks 108. The service provider computers 106 may also include input/output (I/O) device(s) 144, such as a keyboard, a mouse, a pen, a voice input device, a touch input device, a display, one or more speakers, a printer, etc.

Turning to the contents of the memory 136 in more detail, the memory 136 may include an operating system 145 and one or more application programs or services for implementing the features disclosed herein including at least a custom configuration service 146. In some examples, the custom configuration service 146 may be implemented by one or more application programs or features including, but not limited to, user application module 148, a contract module 149, and/or a configurable partition module 150. As used herein, modules may refer to programming modules executed by servers or clusters of servers that are part of a service (e.g., the custom configuration service 146). In this particular context, the modules may be executed by the servers or clusters of servers that are part of the service provider computers 106.

In some examples, the user application module 148 may be configured to, receive, identify, generate, or otherwise manage event streams associated with the users 102. For example, a user 102 may own a business (e.g., an electronic marketplace or the like) that provides event streams via one of the streaming data source computers 110. As such, the user 102 may rely on the service provider computers 106 to manage the data of the event streams. Additionally, in some examples, the users 102 may provide one or more queries (e.g., query 154) for processing incoming event streams associated with their business. As such, based at least in part on the received query 154, and the received event streams, the service provider computers 106 may provide results (e.g., in a user interface (UI) or the like) of the query 154 via the user application module 148.

In some examples, the contract module 149 may be configured to provide a software development kit (SDK) or the like to the users 102 for configuring the partitioning of event streams. Additionally, the contract module 149 may be configured to receive, store, and/or manage one or more custom contracts (e.g., from the users 102) that are developed based at least in part on the SDK or other agreement. The custom contracts may include configuration information 155 that identifies the custom partitions requested by the user 102. In some cases, though, the contract module 149 may be part of and/or work in conjunction with the user application module 148 to provide a UI for configuring the custom partitions without the user 102 writing any code. As such, the UI may provide drop down lists, check boxes, radio buttons, text fields, and/or any other way for the user to indicate the configuration information 155 through the UI.

Additionally, in some examples, the configurable partition module 150 may be configured to receive the configuration information 155 from at least the contract module 149 and the query 154 from the user application module 148. The configurable partition module 150 may also be configured to configure 156 the query 154 based at least in part on the configuration information 155 and the query 154. Once the query 154 is configured 156, the configurable partition module 150 may partition 157 one or more incoming data streams and generate 158 one or more sub-streams. The generated 158 sub-streams may then be provided (e.g., pushed) to the query 154 for processing, and then subsequently provided to the user devices 104 as requested.

Additional types of computer storage media (which may also be non-transitory) that may be present in the service provider computers 106 and/or user devices 104 may include, but are not limited to, programmable random access memory (PRAM), SRAM, DRAM, RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the service provider computers 106 and/or user devices 104. Combinations of any of the above should also be included within the scope of computer-readable storage media.

FIG. 2 depicts a simplified high level diagram of an event processing system 200 that may incorporate an embodiment of the present disclosure. Event processing system 200 may comprise one or more event sources 204, 206, 208, an event processing server (EPS) 202 that is configured to provide an environment for processing event streams, and one or more event sinks 210, 212. The event sources generate event streams that are received by EPS 202. EPS 202 may receive one or more event streams from one or more event sources 204, 206, 208. For example, as shown in FIG. 2, the EPS 202 receives an input event stream 214 from event source 204, a second input event stream 216 from event source 206, and a third event stream 218 from event source 208. One or more event processing applications 220, 222, and 224 may be deployed on and be executed by the EPS 202. An event processing application (e.g., event application 220) executed by the EPS 202 may be configured to listen to one or more input event streams, process the events received via the one or more event streams based upon processing logic that selects one or more events from the input event streams as notable events. The notable events may then be sent to the one or more event sinks 210, 212 in the form of one or more output event streams. For example, in FIG. 2, the EPS 202 outputs an output event stream 226 to event sink 210, and a second output event stream 228 to event sink 212. In certain embodiments, event sources, event processing applications, and event sinks are decoupled from each other such that one can add or remove any of these components without causing changes to the other components.

In one embodiment, the EPS 202 may be implemented as a Java server comprising a lightweight Java application container, such as one based upon Equinox OSGi, with shared services. In some embodiments, the EPS 202 may support ultra-high throughput and microsecond latency for processing events, for example, by using JRockit Real Time. The EPS 202 may also provide a development platform (e.g., a complete real time end-to-end Java Event-Driven Architecture (EDA) development platform) including tools (e.g., Oracle CEP Visualizer and Oracle CEP IDE) for developing event processing applications.

At least one of the event processing applications 220, 222, 224 is configured to listen to one or more input event streams 214, 216, 218, execute logic (e.g., a query) for selecting one or more notable events from the one or more input event streams, and output the selected notable events to one or more event sinks 210, 212 via the one or more output event streams 226, 228. FIG. 2 provides a drilldown for one such event processing application 220 that may in some examples, be configured to perform the features noted above with respect to the custom configuration service 146. As shown in FIG. 2, the event processing application 220 is configured to listen to input event stream 218, execute a query via a CQL engine/CQ service comprising logic for selecting one or more notable events from input event stream 218, and output the selected notable events via output event stream 228 to event sink 212. Examples of event sources include, without limitation, an adapter (e.g., JMS, HTTP, and file), a channel, a processor, a table, a cache, or the like. Examples of event sinks include, without limitation, an adapter (e.g., JMS, HTTP, and file), a channel, a processor, a cache, and the like.

Although event processing application 220 in FIG. 2 is shown as listening to one input stream and outputting selected events via one output stream, this is not intended to be limiting. In alternative embodiments, an event processing application may be configured to listen to multiple input streams received from one or more event sources, select events from the monitored streams, and output the selected events via one or more output event streams to one or more event sinks. The same query can be associated with more than one event sink and with different types of event sinks.

Due to its unbounded nature, the amount of data that is received via an event stream is generally very large. Consequently, it is generally impractical and undesirable to store or archive all the data for querying purposes. The processing of event streams requires processing of the events in real time as the events are received by the EPS 202 without having to store all the received event data. Accordingly, the EPS 202 may provide a special querying mechanism that enables processing of events to be performed as the events are received by the EPS 202 without having to store all the received events.

Event-driven applications may be rule-driven and these rules may be expressed in the form of continuous queries that are used to process input streams. A continuous query may comprise instructions (e.g., business logic) that identify the processing to be performed for received events including what events are to be selected as notable events and output as results of the query processing. Continuous queries may be persisted to a data store and used for processing input streams of events and generating output streams of events. Continuous queries typically perform filtering and aggregation functions to discover and extract notable events from the input event streams. As a result, the number of outbound events in an output event stream is generally much lower than the number of events in the input event stream from which the events are selected.

Unlike a SQL query that is run once on a finite data set, a continuous query that has been registered by an application with the EPS 202 for a particular event stream may be executed each time that an event is received in that event stream. As part of the continuous query execution, the EPS 202 may evaluate the received event based at least in part on instructions specified by the continuous query to determine whether one or more events are to be selected as notable events, and output as a result of the continuous query execution.

The continuous query may be programmed using different languages. In certain embodiments, continuous queries may be configured using the CQL provided by Oracle Corporation and used by Oracle's Complex Events Processing (CEP) product offerings. Oracle's CQL is a declarative language that can be used to program queries (referred to as CQL queries) that can be executed against event streams. In certain embodiments, CQL is based upon SQL with added constructs that support processing of streaming events data.

In one embodiment, an event processing application may be composed of the following component types:

(1) One or more adapters that interface directly to the input and output stream and relation sources and sinks. Adapters are configured to understand the input and output stream protocol, and are responsible for converting the event data into a normalized form that can be queried by an application processor. Adapters may forward the normalized event data into channels or output streams and relation sinks. Event adapters may be defined for a variety of data sources and sinks. (2) One or more channels that act as event processing endpoints. Among other things, channels are responsible for queuing event data until the event processing agent can act upon it. (2) One or more application processors (or event processing agents) are configured to consume normalized event data from a channel, process it using queries to select notable events, and forward (or copy) the selected notable events to an output channel. (4) One or more user-defined Java classes may be implemented to partition the notable events based at least in part on attributes of the event data. In some examples, the even data may then be split up into sub-streams based at least in part on the partitioning, and respective sub-streams can be sent to appropriate output channels. (5) One or more beans are configured to listen to the output channel, and are triggered by the insertion of a new event into the output channel. In some embodiments, this user code is a plain-old-Java-object (POJO). The user application can make use of a set of external services, such as JMS, Web services, and file writers, to forward the generated events to external event sinks. (6) Event beans may be registered to listen to the output channel, and are triggered by the insertion of a new event into the output channel. In some embodiments, this user code may use the Oracle CEP event bean API so that the bean can be managed by Oracle CEP.

In one embodiment, an event adapter provides event data to an input channel. The input channel is connected to a CQL processor associated with one or more CQL queries that operate on the events offered by the input channel. The CQL processor is connected to an output channel to which query results are written.

In some embodiments, an assembly file may be provided for an event processing application describing the various components of the event processing application, how the components are connected together, and event types processed by the application. Separate files may be provided for specifying the continuous query or business logic for selection of events.

It should be appreciated that system 200 depicted in FIG. 2 may have other components than those depicted in FIG. 2. Further, the embodiment shown in FIG. 2 is only one example of a system that may incorporate an embodiment of the present disclosure. In some other embodiments, system 200 may have more or fewer components than shown in FIG. 2, may combine two or more components, or may have a different configuration or arrangement of components. System 200 can be of various types including a personal computer, a portable device (e.g., a mobile telephone or device), a workstation, a network computer, a mainframe, a kiosk, a server, or any other data processing system. In some other embodiments, system 200 may be configured as a distributed system where one or more components of system 200 are distributed across one or more networks in the cloud.

The one or more of the components depicted in FIG. 2 may be implemented in software, in hardware, or combinations thereof. In some embodiments, the software may be stored in memory (e.g., a non-transitory computer-readable medium), on a memory device, or some other physical memory and may be executed by one or more processing units (e.g., one or more processors, one or more processor cores, one or more GPUs, etc.) of the service provider computers 106 or other computing systems.

FIG. 3 depicts a simplified architecture 300 illustrating additional aspects and/or features of the custom configuration service 146 of FIGS. 1 and 2. For example, FIG. 3 illustrates the custom configuration service 146 communicatively coupled to an input data stream 302 (e.g., from one or more streaming sources or channels) and one or more event sinks 304(1)-(N) (collectively, event sinks 304). As seen in FIG. 3, the custom configuration service 146 may also be configured with a query 306 (e.g., like the query 154 of FIG. 1 which may be received from the user 102) for querying the sub-streams (e.g., output of a Java class 308 for processing the data of the input stream 302 either after the query 306 has extracted notable events from the data stream 302 or to modify the query 306). In other words, in some examples, the java class 308 may be modified by the configuration information 155 received from the user 102 of FIG. 1 and utilized to implement the query based at least in part on that configuration information. Additionally, in some examples, when the user provides, registers, and/or configures the query, they may specify one or more Java components that are responsible for partitioning that particular stream. In any case, the Java class 308 may be configured to partition the data of the input stream 302 based at least in part on the user-defined configuration information 155 (e.g., based at least in part on attributes of the data stream 302) using an extension of the higher level event processing language (e.g., tying a Java implementation with a Java interface to the query language).

In some aspects, when the events are partitioned by the custom Java class, each partition may be assigned a partition ID or a bucket ID. One or more application programming interface (API) calls or Java interface calls may be made to put the partitioned events into buckets based at least in part on the partition IDs and/or the bucket IDs. These buckets may be implemented at runtime and may be based at least in part on a hashing of the partitioned data, where the hashing function may be provided by the user. In some examples, each partition may be provided to a respective bucket 310(1)-(N) (collectively, buckets 310), which may then provide the partitioned data to the query 306 via one or more output sub-streams 312(1)-(N) (collectively output sub-streams 312). In some examples, more than one output sub-stream (e.g., output sub-streams 312(1) and 312(2) may provide partitioned data to a query 306, which can manage the partitioned streams itself and may process them in parallel. Examples of partitions provided to query 306 via the output sub-streams 312 include, but are not limited to, IP address from the input stream 302 which appeared more than a certain number of times during a particular period of time, IP address from the input stream 302 which are associated with an account access (e.g., of the user 102) more than a particular number of times during a particular time period, and/or IP address from the input stream 302 with an account name that matches a given string (e.g., during a period of time, or perpetually). The custom configuration service 146 may then process the output sub-streams 312 (e.g., in parallel) using the query 306 (e.g., by pushing the data of the output sub-streams 312 to the query 306) and provide the results to the one or more event sinks 304. In some examples, the query 306 may output a single stream or relation (e.g., to event sink 304(1)) depending on the query construct. However, in other examples, the query 306 may provide multiple streams or relations (e.g., one to each of event sink 304(1) and 304(N)).

In some examples, the query 306 may be associated with the Java class 308 to implement the partitioning by extending the CQL language to support a new data definition for a string. The new data definition may be published in such a way that the partition scheme may be associated with the query component with or without the user writing any code. Additionally, each event may then be received from the stream and passed to a Java engine running on the service provider computers 106. In some cases, an XML file may be utilized to associate the Java class 308 with the query 306 such that the customer configuration service 146 may pick that up at runtime and while processing the event, invoke the Java class 308 to find out which bucket 310 to place the event in, so that they end up in the appropriate sub-stream 312. In order to implement these features, the CQL language may be modified in order to allow the users to associate the Java class 308. Additionally, physical operators that are part of the runtime execution of the CQL engine may be modified to enable the invocation out to the Java class that's being associated. Additionally, each XML file may identify when on what queries to implement each partition scheme. For example, multiple queries may be associated with multiple partitioning schemes and each XML file may be able to identify which partitioning schemes belong to which Java classes, to which queries, to which streams, and/or to what times. Java classes may be reused on multiple different queries and/or data streams. Further, the service provider computers 106 may be configured to provide recommendations and/or suggestions of Java classes to be used for different data streams, business use cases, and/or queries. For example, the event streams may be studied as well as how customers are partitioning them. As such, one partitioning scheme used by one customer may be recommended to another based at least in part on similar event streams, types of data, etc. For example, if it is identified that an event stream of a first customer includes financial information, and the service provider computers 106 further identifies that a second customer processing financial information has utilized certain partitioning schemes, the service provider computers 106 may recommend that the first customer implement the Java class provided by the second customer and/or the partitioning scheme used by the second customer.

Additionally, in some examples, the query 306 may be modified based at least in part on the configuration information 155 received from the user. As noted, the Java class 308 may be configured to modify the query 306 based at least in part on this configuration information 155 in order to partition the input data stream 302 appropriately. In some examples, the query 306 may have originally resembled the following query statements:

View#1 (IPView1):

SELECT ipAddress, acctName

FROM DSLoadChannel1 [RANGE 240 SECONDS]

Query#1 (DSEventIPQuery1):

SELECT ipAddress FROM IPView1

GROUP BY ipAddress HAVING COUNT(1)=100

Query#2 (DSEventIPQuery2):

SELECT ipAddress FROM IPView1

GROUP BY ipAddress, acctName HAVING COUNT(1)=50

Query#3 (DSEventIPQuery3):

SELECT ipAddress FROM IPView1

WHERE acctName LIKE ‘10101010’ GROUP BY ipAddress

In some examples, benchmark data illustrates that the throttle event sender rate for these queries tends to be around 10,000 events per second, revealing the following problem areas:

Scalability Issues

CPU Utilization less than 30%

Increasing number of input threads doesn't scale up the throughput

Lack of Effective Partitioning

Input Thread's run time is ˜40% of their life time

Contention among input threads

In particular, regarding a lack of effective partitioning, one issue appears to be that the thread timeline of the benchmark tests shows a lot thread contention as the run time of each thread is ˜40% of its life time. It appears that this is the case because input data wasn't partitioned effectively on IP address by assuming IP address attribute as a “string” value. A few solutions to this problem include, but are not limited to determining a class (e.g., class A, class B and class C) for each IP address using the IP address octet values, using CQL's extensibility framework to define IP address as an extensible type which will have IP address value as well as its class ID, and defining hashCode( ) method with appropriate hashing mechanism for partitioning the data according to IP Address classes. For example, using the following code as an example:

public class IPAddress {

public String ipAddress;

// getter & setters

@Override

public int hashCode( ) {

-   -   return ipAddress.hashCode( );

}

@Override

public boolean equals(Object obj) {

-   -   if(obj instanceof IPAddress) {         -   IPAddress other=(IPAddress)obj;         -   return this.ipAddress.equals(other.getIpAddress( ));     -   }     -   else         -   return false;

}

}

As well as:

public class DSEvent {

protected IPAddress ipAddress;

protected String acctName;

protected long partitionId;

protected long eventTs;

protected int hashCode;

public DSEvent ( ) { }

-   -   public DSEvent (IPAddress ipAddress, String acctName, long         eventTS, long num, long partitionId)     -   {         -   this.ipAddress=ipAddress;         -   this.acctName=acctName;         -   this.eventTs=eventTS;         -   this.partitionId=partitionId;         -   this.hashCode=(int)num;     -   }

. . .

. . .

}

Regarding the modeling of queries without the current system, one issue appears to be that the usage of database views may not allow for partitioning at least because in the original queries described above, a view named “IPView1” was defined as follows:

-   -   SELECT ipAddress, acctName     -   FROM DSLoadChannel1 [RANGE 240 SECONDS]

However, in the current support of Parallelization using Partitioning, we can't partition a query based on a view source. Thus, the current disclosure describes applying the RANGE WINDOW in a query directly as follows:

-   -   SELECT ipAddress FROM DSLoadChannel1 [RANGE 240 SECONDS]     -   GROUP BY ipAddress     -   HAVING COUNT(ipAddress)=100         Resulting in the following modified queries:         Modified Query 1:     -   SELECT ipAddress     -   FROM DSLoadChannel1[RANGE 240 SECONDS]     -   GROUP BY ipAddress HAVING COUNT(ipAddress)=100         Modified Query 2:     -   SELECT ipAddress     -   FROM DSLoadChannel1[RANGE 240 SECONDS]     -   GROUP BY ipAddress, acctName HAVING COUNT(ipAddress)=50         Modified Query 3:     -   SELECT ipAddress     -   FROM DSLoadChannel1[RANGE 240 SECONDS]     -   WHERE acctName LIKE ‘0101010’     -   GROUP BY ipAddress

As such, the above techniques and features have provided, among other things, a new Java class for IP Address attribute. For example, while creating a new event, creating an instance of class IPAddress with IP Address and its class. Additionally, a mechanism to ensure that a thread in ThrottleEventSender always sends event whose IPAddress belong to same class is introduced. Further, separate stat counters for each thread to reduce the critical section are maintained. At least some of these techniques have led to improved throttle event sender rates, including going from about 10,000 events per second (as described above) to about 50,000 events per second given the same or similar computing environments and associated conditions.

Thus, the described techniques provide support of COUNT aggregate for native OBJECT data type in CQL; fixed Scheduler Thread to send only one timeout heartbeat per invocation irrespective of downstream processing time; an introduction of synchronized mechanisms to ensure that no timeout heartbeat propagation takes place if there is an input waiting on input thread; and introduction of a mechanism to transmit a timeout heartbeat only when the current system time differs from last input's timestamp by more than timeout value. The described techniques also convert IP Address attribute type (among other attribute types) to a CQL extensible data type by defining it as a JAVA class; ensuring in a Throttle Event sender, that each thread sends events having IP addresses belonging to same class; and using simple threads instead of ScheduledThreadPoolExecutor threads.

FIG. 4 depicts a simplified flow diagram showing one or more techniques 400 for implementing the custom partitioning of data streams, according to one example. In FIG. 4, the service provider computers 106 are again shown in communication with the users 102, user devices 104, and/or stream sources 110 via the networks 108. Additionally, in some examples, the service provider computers 106 may include or be in communication (e.g., via the networks 108) with one or more event processor computers and/or databases. While techniques 400 are shown in FIG. 4 in a particular order (including arbitrary sequence numbers), it should be understood that no particular order is necessary and that one or more steps or parts of the techniques 400 may be omitted, skipped, and/or reordered. In at least one non-limiting example, the one or more service provider computers 106 described above with reference to FIGS. 1 and 2 may identify a stream (e.g., associated with a business of the user 102) and/or receive a query from the user for querying events of the stream. In some examples, the service provider computers 106 may also receive code from the user devices 104. The code may be configured to be executed by the service provider computers 106 to interact with or otherwise modify Java code being executed in association with a CEP engine or other even processing server/service/program. The service provider computers 106 may, in some examples, configure the query based at least in part on the code. The code may identify one or more parameters of the stream to partition the data by and/or one or more conditions or rules for partition the data.

In some examples, the service provider computers 106 may also receive streaming data from the one or more stream sources 110 and then partition the results of the stream into buckets and/or sub-streams based at least in part on the received code (e.g., at runtime). As noted, the partitioning may be based on rules, conditions, and/or attributes of the events themselves as defined by the received code. In some examples, the service provider computers 106 may then push the sub-streams to the received query for processing (e.g., in parallel) and then from the query back to the user devices 104 and/or to one or more event sinks.

FIGS. 5 and 6 illustrate example flow diagrams showing respective processes 500 and 600 for implementing the custom partitioning of data streams described herein. These processes 500, 600 are illustrated as logical flow diagrams, each operation of which represents a sequence of operations that can be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, the operations represent computer-executable instructions stored on one or more computer-readable storage media that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures and the like that perform particular functions or implement particular data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the processes.

Additionally, some, any, or all of the processes may be performed under the control of one or more computer systems configured with executable instructions and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) executing collectively on one or more processors, by hardware, or combinations thereof. As noted above, the code may be stored on a computer-readable storage medium, for example, in the form of a computer program comprising a plurality of instructions executable by one or more processors. The computer-readable storage medium may be non-transitory.

In some examples, the one or more service provider computers 106 (e.g., utilizing at least the custom configuration service 146 and/or the configurable partition module 150) shown in FIGS. 1-4 may perform the process 500 of FIG. 5. The process 500 may begin by identifying a query for processing a portion of a data stream associated with a user at 502. As noted, the query may be received from the user and may be configured to query the data stream for real world events. At 504, the process 500 may include receiving code that identifies an attribute of the identified stream. In some examples, the code may be capable of configuring the query based at least in part on an attribute of the events. The process 500 may also include associating the code with the query at 506. The code may be associated with the query in many different ways as described above. For example, the code may be utilized by the service provider computers to modify the query to partition the event data. The code may also be utilized by the service provider computers to modify an event processing engine, some JavaScript, or other processes configured to implement the query.

At 508, the process 500 may include receiving event data of the data stream based at least in part on the query. The process 500 may also include providing each event to a Java class (e.g., based at least in part on the received code) at 510. The Java class may then be implemented to partition the events based at least in part on the attribute at 512. At 514, the process 500 may include receiving output of the Java class implementation (e.g., the sub-streams). The output may include buckets of data that have been partitioned (e.g., each bucket may correspond to a different partition of the data events). At 516, the process 500 may end by configuring the query to process the sub-streams based at least in part on the attributes (e.g., further based at least in part on the implemented Java class).

FIG. 6 illustrates an example flow diagram showing process 600 for implementing the custom partitioning of data streams described herein. The one or more service provider computers 106 (e.g., utilizing at least the custom configuration service 146 and/or the configurable partition module 150) shown in FIGS. 1-4 may perform the process 600 of FIG. 6. The process 600 may begin by identifying a data stream associated with a user (e.g., the user 102 of FIG. 1) at 602. At 604, the process 600 may include determining whether the rate of events being received by the data stream is above a threshold. In some examples, the threshold may include a number that has been identified as problematic and/or that has been known to create issues (e.g., a low throttle event sender rate, a high and/or unmanageable number of input threads, high input thread run time, input thread contention, starving input threads, etc.). In some examples, if it is not determined that the rate of events is above the threshold, the process 600 may include following standard or original partition rules and/or query models to provide a single output stream at 606. Alternatively, if the threshold is reached at 604, the process 600 may include receiving a query from a user at 608. However, in some examples, the query may be received prior to and regardless of the determination at 604.

In some examples, the process may include determining whether a custom configuration code (e.g., configuration information 155) is received at 610. When it is determined that no custom configuration code has been received, the process 600 may include proceeding to 606. However, when custom configuration code is received at 610, and the rate of events is above the threshold, the process 600 may include associating the code with the query at 612. At 614, the process may include passing stream events to code (e.g., a Java server or engine) for partitioning the event data based at least in part on attributes identified in the code. At 616, the process 600 may include providing output sub-streams for each partition/attribute to the query received at 608. Further, the process 600 may end at 618, where the process 600 may include processing the sub-streams using the query (or other query operators including, but not limited to, filter, aggregate, join, etc.). Thus, after the code partitions the event stream into sub-streams, downstream query processing may occur.

FIG. 7 depicts a simplified diagram of a distributed system 700 for implementing one of the embodiments described herein. In the illustrated embodiment, distributed system 700 includes one or more client computing devices 702, 704, 706, and 708, which are configured to execute and operate a client application such as a web browser, proprietary client (e.g., Oracle Forms), or the like over one or more network(s) 710. Server 712 may be communicatively coupled with remote client computing devices 702, 704, 706, and 708 via network 710.

In various embodiments, server 712 may be adapted to run one or more services or software applications provided by one or more of the components of the system. In some embodiments, these services may be offered as web-based or cloud services or under a Software as a Service (SaaS) model to the users of client computing devices 702, 704, 706, and/or 708. Users operating client computing devices 702, 704, 706, and/or 708 may in turn utilize one or more client applications to interact with server 712 to utilize the services provided by these components.

In the configuration depicted in FIG. 7, the software components 718, 720, and 722 of system 700 are shown as being implemented on server 712. In other embodiments, one or more of the components of system 700 and/or the services provided by these components may also be implemented by one or more of the client computing devices 702, 704, 706, and/or 708. Users operating the client computing devices may then utilize one or more client applications to use the services provided by these components. These components may be implemented in hardware, firmware, software, or combinations thereof. It should be appreciated that various different system configurations are possible, which may be different from distributed system 700. The embodiment shown in the FIG. 1 is thus one example of a distributed system for implementing an embodiment system and is not intended to be limiting.

Client computing devices 702, 704, 706, and/or 708 may be portable handheld devices (e.g., an iPhone®), cellular telephone, an iPad®), computing tablet, a personal digital assistant (PDA)) or wearable devices (e.g., a Google Glass® head mounted display), running software such as Microsoft Windows Mobile®, and/or a variety of mobile operating systems such as iOS, Windows Phone, Android, BlackBerry 16, Palm OS, and the like, and being Internet, e-mail, short message service (SMS), Blackberry®, or other communication protocol enabled. The client computing devices can be general purpose personal computers including, by way of example, personal computers, and/or laptop computers running various versions of Microsoft Windows®, Apple Macintosh®, and/or Linux operating systems. The client computing devices can be workstation computers running any of a variety of commercially-available UNIX® or UNIX-like operating systems, including without limitation the variety of GNU/Linux operating systems, such as for example, Google Chrome OS. Alternatively, or in addition, client computing devices 702, 704, 706, and 708 may be any other electronic device, such as a thin-client computer, an Internet-enabled gaming system (e.g., a Microsoft Xbox gaming console with or without a Kinect® gesture input device), and/or a personal messaging device, capable of communicating over network(s) 710.

Although exemplary distributed system 700 is shown with four client computing devices, any number of client computing devices may be supported. Other devices, such as devices with sensors, etc., may interact with server 712.

Network(s) 710 in distributed system 700 may be any type of network familiar to those skilled in the art that can support data communications using any of a variety of commercially-available protocols, including without limitation TCP/IP (transmission control protocol/Internet protocol), SNA (systems network architecture), IPX (Internet packet exchange), AppleTalk, and the like. Merely by way of example, network(s) 710 can be a local area network (LAN), such as one based on Ethernet, Token-Ring and/or the like. Network(s) 710 can be a wide-area network and the Internet. It can include a virtual network, including without limitation a virtual private network (VPN), an intranet, an extranet, a public switched telephone network (PSTN), an infra-red network, a wireless network (e.g., a network operating under any of the Institute of Electrical and Electronics (IEEE) 702.11 suite of protocols, Bluetooth®, and/or any other wireless protocol); and/or any combination of these and/or other networks.

Server 712 may be composed of one or more general purpose computers, specialized server computers (including, by way of example, PC (personal computer) servers, UNIX® servers, mid-range servers, mainframe computers, rack-mounted servers, etc.), server farms, server clusters, or any other appropriate arrangement and/or combination. In various embodiments, server 712 may be adapted to run one or more services or software applications described in the foregoing disclosure. For example, server 712 may correspond to a server for performing processing described above according to an embodiment of the present disclosure.

Server 712 may run an operating system including any of those discussed above, as well as any commercially available server operating system. Server 712 may also run any of a variety of additional server applications and/or mid-tier applications, including HTTP (hypertext transport protocol) servers, FTP (file transfer protocol) servers, CGI (common gateway interface) servers, JAVA® servers, database servers, and the like. Exemplary database servers include without limitation those commercially available from Oracle, Microsoft, Sybase, IBM (International Business Machines), and the like.

In some implementations, server 712 may include one or more applications to analyze and consolidate data feeds and/or event updates received from users of client computing devices 702, 704, 706, and 708. As an example, data feeds and/or event updates may include, but are not limited to, Twitter® feeds, Facebook® updates or real-time updates received from one or more third party information sources and continuous data streams, which may include real-time events related to sensor data applications, financial tickers, network performance measuring tools (e.g., network monitoring and traffic management applications), clickstream analysis tools, automobile traffic monitoring, and the like. Server 712 may also include one or more applications to display the data feeds and/or real-time events via one or more display devices of client computing devices 702, 704, 706, and 708.

Distributed system 700 may also include one or more databases 714 and 716. Databases 714 and 716 may reside in a variety of locations. By way of example, one or more of databases 714 and 716 may reside on a non-transitory storage medium local to (and/or resident in) server 712. Alternatively, databases 714 and 716 may be remote from server 712 and in communication with server 712 via a network-based or dedicated connection. In one set of embodiments, databases 714 and 716 may reside in a storage-area network (SAN). Similarly, any necessary files for performing the functions attributed to server 712 may be stored locally on server 712 and/or remotely, as appropriate. In one set of embodiments, databases 714 and 716 may include relational databases, such as databases provided by Oracle, that are adapted to store, update, and retrieve data in response to SQL-formatted commands.

FIG. 8 is a simplified block diagram of one or more components of a system environment 800 by which services provided by one or more components of an embodiment system may be offered as cloud services, in accordance with an embodiment of the present disclosure. In the illustrated embodiment, system environment 800 includes one or more client computing devices 804, 806, and 808 that may be used by users to interact with a cloud infrastructure system 802 that provides cloud services. The client computing devices may be configured to operate a client application such as a web browser, a proprietary client application (e.g., Oracle Forms), or some other application, which may be used by a user of the client computing device to interact with cloud infrastructure system 802 to use services provided by cloud infrastructure system 802.

It should be appreciated that cloud infrastructure system 802 depicted in the FIG. may have other components than those depicted. Further, the embodiment shown in the FIG. is only one example of a cloud infrastructure system that may incorporate an embodiment of the disclosure. In some other embodiments, cloud infrastructure system 802 may have more or fewer components than shown in the figure, may combine two or more components, or may have a different configuration or arrangement of components.

Client computing devices 804, 806, and 808 may be devices similar to those described above for 702, 704, 706, and 708.

Although exemplary system environment 800 is shown with three client computing devices, any number of client computing devices may be supported. Other devices such as devices with sensors, etc. may interact with cloud infrastructure system 802.

Network(s) 810 may facilitate communications and exchange of data between clients 804, 806, and 808 and cloud infrastructure system 802. Each network may be any type of network familiar to those skilled in the art that can support data communications using any of a variety of commercially-available protocols, including those described above for network(s) 1410.

Cloud infrastructure system 802 may comprise one or more computers and/or servers that may include those described above for server 712.

In certain embodiments, services provided by the cloud infrastructure system may include a host of services that are made available to users of the cloud infrastructure system on demand, such as online data storage and backup solutions, Web-based e-mail services, hosted office suites and document collaboration services, database processing, managed technical support services, and the like. Services provided by the cloud infrastructure system can dynamically scale to meet the needs of its users. A specific instantiation of a service provided by cloud infrastructure system is referred to herein as a “service instance.” In general, any service made available to a user via a communication network, such as the Internet, from a cloud service provider's system is referred to as a “cloud service.” Typically, in a public cloud environment, servers and systems that make up the cloud service provider's system are different from the customer's own on-premises servers and systems. For example, a cloud service provider's system may host an application, and a user may, via a communication network such as the Internet, on demand, order and use the application.

In some examples, a service in a computer network cloud infrastructure may include protected computer network access to storage, a hosted database, a hosted web server, a software application, or other service provided by a cloud vendor to a user, or as otherwise known in the art. For example, a service can include password-protected access to remote storage on the cloud through the Internet. As another example, a service can include a web service-based hosted relational database and a script-language middleware engine for private use by a networked developer. As another example, a service can include access to an email software application hosted on a cloud vendor's web site.

In certain embodiments, cloud infrastructure system 802 may include a suite of applications, middleware, and database service offerings that are delivered to a customer in a self-service, subscription-based, elastically scalable, reliable, highly available, and secure manner. An example of such a cloud infrastructure system is the Oracle Public Cloud provided by the present assignee.

In various embodiments, cloud infrastructure system 802 may be adapted to automatically provision, manage, and track a customer's subscription to services offered by cloud infrastructure system 802. Cloud infrastructure system 802 may provide the cloud services via different deployment models. For example, services may be provided under a public cloud model in which cloud infrastructure system 802 is owned by an organization selling cloud services (e.g., owned by Oracle) and the services are made available to the general public or different industry enterprises. As another example, services may be provided under a private cloud model in which cloud infrastructure system 802 is operated solely for a single organization and may provide services for one or more entities within the organization. The cloud services may also be provided under a community cloud model in which cloud infrastructure system 802 and the services provided by cloud infrastructure system 802 are shared by several organizations in a related community. The cloud services may also be provided under a hybrid cloud model, which is a combination of two or more different models.

In some embodiments, the services provided by cloud infrastructure system 802 may include one or more services provided under Software as a Service (SaaS) category, Platform as a Service (PaaS) category, Infrastructure as a Service (IaaS) category, or other categories of services including hybrid services. A customer, via a subscription order, may order one or more services provided by cloud infrastructure system 802. Cloud infrastructure system 802 then performs processing to provide the services in the customer's subscription order.

In some embodiments, the services provided by cloud infrastructure system 802 may include, without limitation, application services, platform services and infrastructure services. In some examples, application services may be provided by the cloud infrastructure system via a SaaS platform. The SaaS platform may be configured to provide cloud services that fall under the SaaS category. For example, the SaaS platform may provide capabilities to build and deliver a suite of on-demand applications on an integrated development and deployment platform. The SaaS platform may manage and control the underlying software and infrastructure for providing the SaaS services. By utilizing the services provided by the SaaS platform, customers can utilize applications executing on the cloud infrastructure system. Customers can acquire the application services without the need for customers to purchase separate licenses and support. Various different SaaS services may be provided. Examples include, without limitation, services that provide solutions for sales performance management, enterprise integration, and business flexibility for large organizations.

In some embodiments, platform services may be provided by the cloud infrastructure system via a PaaS platform. The PaaS platform may be configured to provide cloud services that fall under the PaaS category. Examples of platform services may include without limitation services that enable organizations (such as Oracle) to consolidate existing applications on a shared, common architecture, as well as the ability to build new applications that leverage the shared services provided by the platform. The PaaS platform may manage and control the underlying software and infrastructure for providing the PaaS services. Customers can acquire the PaaS services provided by the cloud infrastructure system without the need for customers to purchase separate licenses and support. Examples of platform services include, without limitation, Oracle Java Cloud Service (JCS), Oracle Database Cloud Service (DBCS), and others.

By utilizing the services provided by the PaaS platform, customers can employ programming languages and tools supported by the cloud infrastructure system and also control the deployed services. In some embodiments, platform services provided by the cloud infrastructure system may include database cloud services, middleware cloud services (e.g., Oracle Fusion Middleware services), and Java cloud services. In one embodiment, database cloud services may support shared service deployment models that enable organizations to pool database resources and offer customers a Database as a Service in the form of a database cloud. Middleware cloud services may provide a platform for customers to develop and deploy various business applications, and Java cloud services may provide a platform for customers to deploy Java applications, in the cloud infrastructure system.

Various different infrastructure services may be provided by an IaaS platform in the cloud infrastructure system. The infrastructure services facilitate the management and control of the underlying computing resources, such as storage, networks, and other fundamental computing resources for customers utilizing services provided by the SaaS platform and the PaaS platform.

In certain embodiments, cloud infrastructure system 802 may also include infrastructure resources 830 for providing the resources used to provide various services to customers of the cloud infrastructure system. In one embodiment, infrastructure resources 830 may include pre-integrated and optimized combinations of hardware, such as servers, storage, and networking resources to execute the services provided by the PaaS platform and the SaaS platform.

In some embodiments, resources in cloud infrastructure system 802 may be shared by multiple users and dynamically re-allocated per demand. Additionally, resources may be allocated to users in different time zones. For example, cloud infrastructure system 830 may enable a first set of users in a first time zone to utilize resources of the cloud infrastructure system for a specified number of hours and then enable the re-allocation of the same resources to another set of users located in a different time zone, thereby maximizing the utilization of resources.

In certain embodiments, a number of internal shared services 832 may be provided that are shared by different components or modules of cloud infrastructure system 802 and by the services provided by cloud infrastructure system 802. These internal shared services may include, without limitation, a security and identity service, an integration service, an enterprise repository service, an enterprise manager service, a virus scanning and white list service, a high availability, backup and recovery service, service for enabling cloud support, an email service, a notification service, a file transfer service, and the like.

In certain embodiments, cloud infrastructure system 802 may provide comprehensive management of cloud services (e.g., SaaS, PaaS, and IaaS services) in the cloud infrastructure system. In one embodiment, cloud management functionality may include capabilities for provisioning, managing, and tracking a customer's subscription received by cloud infrastructure system 802, and the like.

In one embodiment, as depicted in the figure, cloud management functionality may be provided by one or more modules, such as an order management module 820, an order orchestration module 822, an order provisioning module 824, an order management and monitoring module 826, and an identity management module 828. These modules may include or be provided using one or more computers and/or servers, which may be general purpose computers, specialized server computers, server farms, server clusters, or any other appropriate arrangement and/or combination.

In exemplary operation 834, a customer using a client device, such as client device 804, 806 or 808, may interact with cloud infrastructure system 802 by requesting one or more services provided by cloud infrastructure system 802 and placing an order for a subscription for one or more services offered by cloud infrastructure system 802. In certain embodiments, the customer may access a cloud User Interface (UI), cloud UI 812, cloud UI 814, and/or cloud UI 816 and place a subscription order via these UIs. The order information received by cloud infrastructure system 802 in response to the customer placing an order may include information identifying the customer and one or more services offered by the cloud infrastructure system 802 that the customer intends to subscribe to.

After an order has been placed by the customer, the order information is received via the cloud UIs, 812, 814, and/or 816.

At operation 836, the order is stored in order database 818. Order database 818 can be one of several databases operated by cloud infrastructure system 818 and operated in conjunction with other system elements.

At operation 838, the order information is forwarded to an order management module 820. In some instances, order management module 820 may be configured to perform billing and accounting functions related to the order, such as verifying the order, and upon verification, booking the order.

At operation 840, information regarding the order is communicated to an order orchestration module 822. Order orchestration module 822 may utilize the order information to orchestrate the provisioning of services and resources for the order placed by the customer. In some instances, order orchestration module 822 may orchestrate the provisioning of resources to support the subscribed services using the services of order provisioning module 824.

In certain embodiments, order orchestration module 822 enables the management of business processes associated with each order and applies business logic to determine whether an order should proceed to provisioning. At operation 842, upon receiving an order for a new subscription, order orchestration module 822 sends a request to order provisioning module 824 to allocate resources and configure those resources needed to fulfill the subscription order. Order provisioning module 824 enables the allocation of resources for the services ordered by the customer. Order provisioning module 824 provides a level of abstraction between the cloud services provided by cloud infrastructure system 800 and the physical implementation layer that is used to provision the resources for providing the requested services. Order orchestration module 822 may thus be isolated from implementation details, such as whether or not services and resources are actually provisioned on the fly or pre-provisioned and only allocated/assigned upon request.

At operation 844, once the services and resources are provisioned, a notification of the provided service may be sent to customers on client devices 804, 806, and/or 808 by order provisioning module 824 of cloud infrastructure system 802.

At operation 846, the customer's subscription order may be managed and tracked by an order management and monitoring module 826. In some instances, order management and monitoring module 826 may be configured to collect usage statistics for the services in the subscription order, such as the amount of storage used, the amount data transferred, the number of users, and the amount of system up time and system down time.

In certain embodiments, cloud infrastructure system 800 may include an identity management module 828. Identity management module 828 may be configured to provide identity services, such as access management and authorization services in cloud infrastructure system 800. In some embodiments, identity management module 828 may control information about customers who wish to utilize the services provided by cloud infrastructure system 802. Such information can include information that authenticates the identities of such customers and information that describes which actions those customers are authorized to perform relative to various system resources (e.g., files, directories, applications, communication ports, memory segments, etc.) Identity management module 828 may also include the management of descriptive information about each customer and about how and by whom that descriptive information can be accessed and modified.

FIG. 9 illustrates an exemplary computer system 900, in which various embodiments of the present disclosure may be implemented. The system 900 may be used to implement any of the computer systems described above. As shown in the figure, computer system 900 includes a processing unit 904 that communicates with a number of peripheral subsystems via a bus subsystem 902. These peripheral subsystems may include a processing acceleration unit 906, an I/O subsystem 908, a storage subsystem 918, and a communications subsystem 924. Storage subsystem 918 includes tangible computer-readable storage media 922 and a system memory 910.

Bus subsystem 902 provides a mechanism for letting the various components and subsystems of computer system 900 communicate with each other as intended. Although bus subsystem 902 is shown schematically as a single bus, alternative embodiments of the bus subsystem may utilize multiple buses. Bus subsystem 902 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. For example, such architectures may include an Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus, which can be implemented as a Mezzanine bus manufactured to the IEEE P1386.1 standard.

Processing unit 904, which can be implemented as one or more integrated circuits (e.g., a conventional microprocessor or microcontroller), controls the operation of computer system 900. One or more processors may be included in processing unit 904. These processors may include single core or multicore processors. In certain embodiments, processing unit 904 may be implemented as one or more independent processing units 932 and/or 934 with single or multicore processors included in each processing unit. In other embodiments, processing unit 904 may also be implemented as a quad-core processing unit formed by integrating two dual-core processors into a single chip.

In various embodiments, processing unit 904 can execute a variety of programs in response to program code and can maintain multiple concurrently executing programs or processes. At any given time, some or all of the program code to be executed can be resident in processor(s) 904 and/or in storage subsystem 918. Through suitable programming, processor(s) 904 can provide various functionalities described above. Computer system 900 may additionally include a processing acceleration unit 906, which can include a digital signal processor (DSP), a special-purpose processor, and/or the like.

I/O subsystem 908 may include user interface input devices and user interface output devices. User interface input devices may include a keyboard, pointing devices such as a mouse or trackball, a touchpad or touch screen incorporated into a display, a scroll wheel, a click wheel, a dial, a button, a switch, a keypad, audio input devices with voice command recognition systems, microphones, and other types of input devices. User interface input devices may include, for example, motion sensing and/or gesture recognition devices such as the Microsoft Kinect® motion sensor that enables users to control and interact with an input device, such as the Microsoft Xbox® 360 game controller, through a natural user interface using gestures and spoken commands. User interface input devices may also include eye gesture recognition devices such as the Google Glass® blink detector that detects eye activity (e.g., ‘blinking’ while taking pictures and/or making a menu selection) from users and transforms the eye gestures as input into an input device (e.g., Google Glass®). Additionally, user interface input devices may include voice recognition sensing devices that enable users to interact with voice recognition systems (e.g., Siri® navigator), through voice commands.

User interface input devices may also include, without limitation, three dimensional (3D) mice, joysticks or pointing sticks, gamepads and graphic tablets, and audio/visual devices such as speakers, digital cameras, digital camcorders, portable media players, webcams, image scanners, fingerprint scanners, barcode reader 3D scanners, 3D printers, laser rangefinders, and eye gaze tracking devices. Additionally, user interface input devices may include, for example, medical imaging input devices such as computed tomography, magnetic resonance imaging, position emission tomography, medical ultrasonography devices. User interface input devices may also include, for example, audio input devices such as MIDI keyboards, digital musical instruments and the like.

User interface output devices may include a display subsystem, indicator lights, or non-visual displays such as audio output devices, etc. The display subsystem may be a cathode ray tube (CRT), a flat-panel device, such as that using a liquid crystal display (LCD) or plasma display, a projection device, a touch screen, and the like. In general, use of the term “output device” is intended to include all possible types of devices and mechanisms for outputting information from computer system 900 to a user or other computer. For example, user interface output devices may include, without limitation, a variety of display devices that visually convey text, graphics and audio/video information such as monitors, printers, speakers, headphones, automotive navigation systems, plotters, voice output devices, and modems.

Computer system 900 may comprise a storage subsystem 918 that comprises software elements, shown as being currently located within a system memory 910. System memory 910 may store program instructions that are loadable and executable on processing unit 904, as well as data generated during the execution of these programs.

Depending on the configuration and type of computer system 900, system memory 910 may be volatile (such as random access memory (RAM)) and/or non-volatile (such as read-only memory (ROM), flash memory, etc.) The RAM typically contains data and/or program modules that are immediately accessible to and/or presently being operated and executed by processing unit 904. In some implementations, system memory 910 may include multiple different types of memory, such as static random access memory (SRAM) or dynamic random access memory (DRAM). In some implementations, a basic input/output system (BIOS), containing the basic routines that help to transfer information between elements within computer system 900, such as during start-up, may typically be stored in the ROM. By way of example, and not limitation, system memory 910 also illustrates application programs 912, which may include client applications, Web browsers, mid-tier applications, relational database management systems (RDBMS), etc., program data 914, and an operating system 916. By way of example, operating system 916 may include various versions of Microsoft Windows®, Apple Macintosh®, and/or Linux operating systems, a variety of commercially-available UNIX® or UNIX-like operating systems (including without limitation the variety of GNU/Linux operating systems, the Google Chrome® OS, and the like) and/or mobile operating systems such as iOS, Windows® Phone, Android® OS, BlackBerry® 9 OS, and Palm® OS operating systems.

Storage subsystem 918 may also provide a tangible computer-readable storage medium for storing the basic programming and data constructs that provide the functionality of some embodiments. Software (programs, code modules, instructions) that when executed by a processor provide the functionality described above may be stored in storage subsystem 918. These software modules or instructions may be executed by processing unit 904. Storage subsystem 918 may also provide a repository for storing data used in accordance with the present disclosure.

Storage subsystem 900 may also include a computer-readable storage media reader 920 that can further be connected to computer-readable storage media 922. Together and, optionally, in combination with system memory 910, computer-readable storage media 922 may comprehensively represent remote, local, fixed, and/or removable storage devices plus storage media for temporarily and/or more permanently containing, storing, transmitting, and retrieving computer-readable information.

Computer-readable storage media 922 containing code, or portions of code, can also include any appropriate media known or used in the art, including storage media and communication media, such as but not limited to, volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage and/or transmission of information. This can include tangible computer-readable storage media such as RAM, ROM, electronically erasable programmable ROM (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disk (DVD), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other tangible computer readable media. This can also include nontangible computer-readable media, such as data signals, data transmissions, or any other medium which can be used to transmit the desired information and which can be accessed by computing system 900.

By way of example, computer-readable storage media 922 may include a hard disk drive that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive that reads from or writes to a removable, nonvolatile magnetic disk, and an optical disk drive that reads from or writes to a removable, nonvolatile optical disk such as a CD ROM, DVD, and Blu-Ray® disk, or other optical media. Computer-readable storage media 922 may include, but is not limited to, Zip® drives, flash memory cards, universal serial bus (USB) flash drives, secure digital (SD) cards, DVD disks, digital video tape, and the like. Computer-readable storage media 922 may also include, solid-state drives (SSD) based on non-volatile memory such as flash-memory based SSDs, enterprise flash drives, solid state ROM, and the like, SSDs based on volatile memory such as solid state RAM, dynamic RAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, and hybrid SSDs that use a combination of DRAM and flash memory based SSDs. The disk drives and their associated computer-readable media may provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for computer system 900.

Communications subsystem 924 provides an interface to other computer systems and networks. Communications subsystem 924 serves as an interface for receiving data from and transmitting data to other systems from computer system 900. For example, communications subsystem 924 may enable computer system 900 to connect to one or more devices via the Internet. In some embodiments communications subsystem 924 can include radio frequency (RF) transceiver components for accessing wireless voice and/or data networks (e.g., using cellular telephone technology, advanced data network technology, such as 3G, 4G or EDGE (enhanced data rates for global evolution), WiFi (IEEE 1402.11 family standards, or other mobile communication technologies, or any combination thereof), global positioning system (GPS) receiver components, and/or other components. In some embodiments communications subsystem 924 can provide wired network connectivity (e.g., Ethernet) in addition to or instead of a wireless interface.

In some embodiments, communications subsystem 924 may also receive input communication in the form of structured and/or unstructured data feeds 926, event streams 928, event updates 930, and the like on behalf of one or more users who may use computer system 900.

By way of example, communications subsystem 924 may be configured to receive data feeds 926 in real-time from users of social networks and/or other communication services such as Twitter® feeds, Facebook® updates, web feeds such as Rich Site Summary (RSS) feeds, and/or real-time updates from one or more third party information sources.

Additionally, communications subsystem 924 may also be configured to receive data in the form of continuous data streams, which may include event streams 928 of real-time events and/or event updates 930, that may be continuous or unbounded in nature with no explicit end. Examples of applications that generate continuous data may include, for example, sensor data applications, financial tickers, network performance measuring tools (e.g. network monitoring and traffic management applications), clickstream analysis tools, automobile traffic monitoring, and the like.

Communications subsystem 924 may also be configured to output the structured and/or unstructured data feeds 926, event streams 928, event updates 930, and the like to one or more databases that may be in communication with one or more streaming data source computers coupled to computer system 900.

Computer system 900 can be one of various types, including a handheld portable device (e.g., an iPhone® cellular phone, an iPad® computing tablet, a PDA), a wearable device (e.g., a Google Glass® head mounted display), a PC, a workstation, a mainframe, a kiosk, a server rack, or any other data processing system.

Due to the ever-changing nature of computers and networks, the description of computer system 900 depicted in the FIG. 1 is intended only as a specific example. Many other configurations having more or fewer components than the system depicted in the FIG. are possible. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, firmware, software (including applets), or a combination. Further, connection to other computing devices, such as network input/output devices, may be employed. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate other ways and/or methods to implement the various embodiments.

In the foregoing specification, aspects of the disclosure are described with reference to specific embodiments thereof, but those skilled in the art will recognize that the disclosure is not limited thereto. Various features and aspects of the above-described disclosure may be used individually or jointly. Further, embodiments can be utilized in any number of environments and applications beyond those described herein without departing from the broader spirit and scope of the specification. The specification and drawings are, accordingly, to be regarded as illustrative rather than restrictive. 

What is claimed is:
 1. A system, comprising: a memory storing computer-executable instructions; and a processor configured to access the memory and execute the computer-executable instructions to at least: identify a data stream associated with a user; receive a query for processing at least a portion of the data stream; identify a rate of events of the data stream, the rate of events comprising a number of events received by the processor per time period; determine that the rate of events is above a threshold; and when the rate of events is above the threshold: provide, to the user, a software development kit for generating a java class; enable the user to create a partition class in java using the software development kit, the partition class configured to: receive each event of the data stream at runtime; and partition the data stream into a plurality of sub-stream portions; receive, from the user, an attribute of the data stream; receive, from the user, the partition class generated by the user for partitioning the data stream, the partition class is based at least in part on the software development kit and the attribute of the data stream; associate, by the computer system, the partition class with the query; process each event of the data stream with the partition class at runtime to partition the data stream based at least in part on the association of the partition class with the query; the process comprising: partitioning the data stream into the plurality of sub-stream portions based at least in part on the attribute; provide at least one sub-stream portion of the plurality of sub-stream portions to the query; process the at least one sub-stream portion, using the query, in parallel with at least a second sub-stream portion of the plurality of sub-stream portions that is received as an output from the partition class; and provide results of the query based at least in part on the at least one sub-stream portion and the second sub-stream portion.
 2. The system of claim 1, wherein associating the partition class with the query comprises tying the query to the partition class.
 3. The system of claim 2, wherein the processor is further configured to execute the computer-executable instructions to at least: receive an event of the data stream based at least in part on the query; provide the event to the partition class; and receive an output from the partition class.
 4. The system of claim 3, wherein the data stream is partitioned based at least in part on the output from the partition class.
 5. The system of claim 1, wherein the attribute comprises at least one of a first identifier of a computing device of a customer of the user, a second identifier of an item associated with the user, or a third identifier of an item attribute associated with the item.
 6. The system of claim 5, wherein the identifier of the computing device of the customer indicates an Internet Protocol address of the computing device of the customer or a geographic region in which the computing device of the customer is located.
 7. A non-transitory computer-readable storage memory storing a plurality of instructions executable by one or more processors, the plurality of instructions comprising: instructions to identify a query for processing at least a portion of a data stream associated with a user; instructions to identify the data stream associated with the user; instructions to identify a rate of events of the data stream, the rate of events comprising a number of events received per time period; instructions to determine that the rate of events is above a threshold; and when the rate of events is above the threshold, the plurality of instructions further comprise: instructions to provide a software development kit to the user; instructions to enable the user to create a partition class in java using the software development kit, the partition class is configured to: receive each event of the data stream at runtime; an partition the data stream into a plurality of sub-stream portions; instructions to receive, from the user, an attribute of the data stream; instructions to receive, from the user, the partition class generated by the user for partitioning the data stream, the partition class is identifying the attribute of the data stream and is generated based at least in part on the software development kit; instructions to process each event of the data stream with the partition class at runtime to partition the data stream based at least in part on an association of the partition class with the query, the processing of each event comprising: partitioning the data stream into the plurality of sub-stream portions based at least in part on the attribute; an instructions to configure the query to process at least one sub stream portion of the plurality of sub-stream portions in parallel with at least a second sub-stream portion of the plurality of sub-stream portions that is received as an output from the partition class; and instructions to provide results of the query based at least in part on the at least one sub-stream portion and the at least one second sub-stream portion.
 8. The non-transitory computer-readable storage memory of claim 7, wherein the plurality of instructions further comprise: instructions to receive an event of the data stream based at least in part on the query; instructions to provide the event to the partition class; instructions to implement the partition class to process the event based at least in part on the attribute; and instructions to receive an output from the partition class.
 9. The non-transitory computer-readable storage memory of claim 8, wherein the output from the partition class is at least one of the plurality of sub-stream portions.
 10. The non-transitory computer-readable storage memory of claim 7, wherein the attribute is specified by the user prior to receipt of the partition class.
 11. The non-transitory computer-readable storage memory of claim 7, wherein at least one sub-stream of the plurality of sub-stream portions is generated based at least in part on a hashing function performed on the at least a portion of the data stream.
 12. A computer-implemented method, comprising: identifying, by a computing system, a data stream associated with a user, receiving a query for processing at least a portion of the data stream; identifying a rate of events of the data stream, the rate of events comprising a number of events received by the computing system per time period; determining that the rate of events is above a threshold; and when the rate of events is above the threshold: receiving, from the user, a partition class in java identifying an attribute of the data stream, the partition class is based at least in part on a software development kit received by the user, and the partition class is configured to: receive each event of the data stream; and partition the data stream into a plurality of sub-stream portions based at least in part on the attribute; executing the partition class at runtime to partition the data stream into at least one sub-stream portion of the plurality of sub-stream portions based at least in part on the attribute and an association of the partition class with the query; processing the at least one sub-stream using the query in parallel with at least a second sub-stream portion of the plurality of sub-stream portions that is received as an output from the partition class; and providing results of the query based at least in part on the at least one sub-stream portion and the second sub-stream portion.
 13. The computer-implemented method of claim 12, wherein the sub-stream portion is generated based at least in part on a hashing function performed on at least one of the plurality of sub-stream portions.
 14. The computer-implemented method of claim 12, wherein the attribute comprises at least one of an Internet Protocol address associated with a customer of the user or a geographic region associated with the customer of the user. 